-
Notifications
You must be signed in to change notification settings - Fork 142
New changes / features for composefs-backend #1644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New changes / features for composefs-backend #1644
Conversation
3e03d56
to
b4cd3c2
Compare
b4cd3c2
to
6134880
Compare
82ee61e
to
ebe252c
Compare
Currently with the option Does it make sense to do the above until we have systemd-boot support in bootupd? |
Yes I'll try to take a look at coreos/bootupd#978 soon. Otherwise see #806 (comment) - I think the "no bootupd = systemd-boot" path also makes sense and should be relatively straightforward to implement here. |
Ah my bad, I think we have some textual (partial semantic) conflicts in #1662 |
That's okay. I can rebase on main afterwards |
crates/lib/src/install.rs
Outdated
|
||
#[cfg(feature = "composefs-backend")] | ||
#[clap(flatten)] | ||
pub(crate) compoesfs_opts: InstallComposefsOpts, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's your opinion on adding something like typos to the CI? There are quite a few typos across the repo
b0b66d3
to
791fc9a
Compare
Signed-off-by: Pragyan Poudyal <[email protected]> Signed-off-by: Colin Walters <[email protected]>
We were using composefs-native and composefs-backend interchangeably. Replace all instances of `composefs-native` with `composefs-backend` Move all composefs-backend options to a single struct so that we can test for boolean instead of testing for Some/None for composefs-backend options Signed-off-by: Pragyan Poudyal <[email protected]> Signed-off-by: Colin Walters <[email protected]>
Instead of storing the source imgref in the .origin file, we store the target imgref Signed-off-by: Pragyan Poudyal <[email protected]> Signed-off-by: Colin Walters <[email protected]>
Rename service to bootc-finalize-staged Signed-off-by: Pragyan Poudyal <[email protected]> Signed-off-by: Colin Walters <[email protected]>
791fc9a
to
c268ac2
Compare
I rebased this one |
OK, the new composefs test fails on this one; it's possible I broke something when rebasing, or it's a legit regression. |
Signed-off-by: Pragyan Poudyal <[email protected]> Signed-off-by: Colin Walters <[email protected]>
c268ac2
to
1d384c4
Compare
So, |
Gate some lines behind composefs-backend feature Signed-off-by: Pragyan Poudyal <[email protected]>
a5b8afa
to
9243712
Compare
Finish up implementation for
install-to-filesystem
forcomposefs-backend
We were using composefs-native and composefs-backend interchangeably.
Replace all instances of
composefs-native
withcomposefs-backend
Move all composefs-backend options to a single struct so that we can
test for boolean instead of testing for Some/None for composefs-backend
options
The source imgref was being stored in the .origin file, even if target imgref was
provided. Now we store the target imgref
Start finalize-staged service on update/switch
Add composefs opts to install-to-existing-root